Thanks the patch @adoroszlai. I like the approach to reverse the dependency (and simplify acceptance.sh and unit.sh), but I would prefer to keep the feature to separate certain type of integration tests as in this branch/runs:

https://github.com/apache/hadoop-ozone/runs/373475163

The test execution of integration-test project is already very slow, we can make it faster with separating contract/tools tests. I am not sure how to do it in this new structure. We have multiple options:

1. put everything to the integration-test and use profiles to separate tests
2. create separated integration-test/contract and integration-test/tools projects
3. Keep the tests in the original projects and use the maven integration-test phase to execute these tests.

What is your preference?

Thanks @elek for bringing this up.

1. put everything to the integration-test and use profiles to separate tests
2. create separated integration-test/contract and integration-test/tools projects
3. Keep the tests in the original projects and use the maven integration-test phase to execute these tests.

What is your preference?

I think option 1 would give us the most fine-grained control for grouping tests to ensure similar run time of the parallel jobs.

I think option 1 would give us the most fine-grained control for grouping tests to ensure similar run time of the parallel jobs.

In this case let me commit this one, and we can introduce the new profiles in the patch where the integration tests are enabled...

Thanks @elek for reviewing and committing this.